Rewrite landing hero closing copy into a "so what + what's coming" hook#83
Merged
Conversation
The hero's closing caption only stated negatives ("no separate frontend,
no build step, no generated code") and never told the reader the payoff or
teased the spine that follows, so the "real, not a toy" claim went unearned.
Replace it with a two-beat block in relatable terminology (SPA, REST API,
frontend framework, progressive enhancement, real-time): first the payoff
the literal 20-line greet app already delivers (live in-place updates, no
reload, no JavaScript written), then the real-app features that are "a small
diff on this exact code" — validation, loading, progressive enhancement,
cross-tab sync, multi-user, uploads — which are exactly what the rest of the
page builds. Progressive enhancement stays in the "diff away" bucket since
the storeless hero greet doesn't persist across a no-JS POST.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Rewrites the landing hero's closing caption (
content/index.md). It previously stated only negatives — "No separate frontend, no build step, no generated code" — and never told the reader the payoff or teased the spine that follows, so the "real app, not a toy" claim (which lands one section later) went unearned.The new copy is a two-beat block, in relatable terminology (SPA, REST API, frontend framework, progressive enhancement, real-time):
greetapp already delivers — live in-place updates, no full reload, no JavaScript you had to write.Accuracy note
The hero embeds the storeless
examples/greet(state re-cloned to initial on every fresh request), so "works without JavaScript" is deliberately kept in the diff-away bucket as "progressive enhancement" — the bare 20 lines submit a plain POST but render the default; persisting across a no-JS round-trip needs the separategreet-nojsstore. No claim is made that the literal hero app works identically with JS off.Verification
tinkerdown validate content/— 93/93 pages, 0 errorsGOWORK=off go test ./cmd/... ./examples/...green🤖 Generated with Claude Code